UCP/PROTO: Refactoring: move perf node into ucp_proto_perf_node_t #11101
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
guy-ealey-morag
approved these changes
Jan 6, 2026
iyastreb
force-pushed
the
ucp-multi-proto-refactoring
branch
from
4c72e7e to
300400e
Compare
iyastreb
force-pushed
the
ucp-multi-proto-refactoring
branch
from
300400e to
30fa660
Compare
brminich
approved these changes
Jan 9, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Minor refactoring that moves perf node into ucp_proto_perf_node_t structure.
These 2 structures are always used together and related 1:1. This will simplify implementation of the lane selection variants (#10778)
Why?
The goals of this refactoring are: